-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stable UNIX users: functionality #51200
Conversation
return nil, trace.BadParameter("missing Emitter") | ||
} | ||
if c.Logger == nil { | ||
return nil, trace.BadParameter("missing Logger") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use slog.Default instead of failing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the one place where we call this in real code we have access to the logger from the auth server - we can let the caller specify a default or noop logger, IMO.
58c1a94
to
8fe2aba
Compare
@eriktate friendly ping |
* wiring the API client through * tctl stable-unix-users ls * stable UID fallback for Teleport SSHD * stable_unix_user.create event * fix-license * Require and test audit log message * Add stable_unix_user_config to fileconf * Avoid saying "fallback UID" in logs * Avoid saying "fallback UID" in error messages * Avoid racing writes in the mock emitter * pnpm lint-fix * fix lib/auth tests that broken during rebase
This PR adds the use of fallback UIDs for host user creation in the Teleport SSHd and a
tctl
subcommand (tctl stable-unix-users ls
) to list the persisted usernames and their UIDs. This PR also adds an audit log event to the API, emitted when a new username is written, and support for configuring the feature in the auth server's config file.Related RFD: #50414
Part of #50292